[DO NOT MERGE] [SMP-2881] Empty state in events dashboard after a forced logout due to a refresh token error#3
Draft
dgonzalez-splashthat wants to merge 1 commit intosecondaryindex-search-2.7.3from
Conversation
…o a refresh token error
| #define DEFAULT_MAX_CONNECTION_POOL_COUNT 5 // connections | ||
| #define DEFAULT_CONNECTION_POOL_LIFETIME 90.0 // seconds | ||
|
|
||
| static BOOL logToConsole = NO; |
Author
There was a problem hiding this comment.
Only a few things changed here. XCode has automatically indented this file.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DO NOT MERGE
This PR has been created just to review the differences between branches.
This branch is referenced by the iOS HostApp in the Podfile.
What are you trying to accomplish?
Additional Description
Customers are complaining about seeing an empty events list after a BE forced logout.
This is a random problem that doesn't happen frequently. We cannot reproduce it, but we are sure it's a database issue caused by not properly disposed open connections after a logout.
In order to analyze this, we have to add some logic to the YapDatabase library that keeps track of connections state, and send a report to Datadog when they aren't properly closed, telling where in the code that connection is in use.
We have to:
Slack conversation: https://cvent.slack.com/archives/C0844C6DV0C/p1747255741587129